Tree

There is a problem

1000 entries with tree-preservation-order field must match the reference field in the tree preservation order

1602

reference: 216-tree-1
name: 1602
tree-preservation-order: undefined
216-tpo-1
uprn
address-text
point: POINT (-1.043918 50.894937)
geometry: MULTIPOLYGON (((-1.043762 50.894921,-1.043769 50.894951,-1.043791 50.894979,-1.043825 50.895001,-1.043868 50.895016,-1.043916 50.895021,-1.043965 50.895017,-1.044009 50.895003,-1.044044 50.894981,-1.044066 50.894954,-1.044075 50.894923,-1.044068 50.894893,-1.044046 50.894865,-1.044012 50.894843,-1.043969 50.894828,-1.043920 50.894823,-1.043872 50.894828,-1.043828 50.894841,-1.043793 50.894863,-1.043770 50.894890,-1.043762 50.894921)))
notes
felled-date
entry-date: 2026-08-06
start-date
end-date

How to fix this issue

Your data is missing a tree-preservation-order.

The tree guidance explains how to fix the issue:

tree-preservation-order

The reference for the tree preservation order that affects this tree.

Example: TPO1

This diagram shows the relationship between the tree preservation order dataset and the tree dataset. The reference value from your tree preservation order dataset needs to match the tree-preservation-order value in your tree dataset.

How to improve East Hampshire District Council’s data

Fix the errors indicated
Use the check service to make sure the data meets the standard
Publish the updated data on the endpoint URL